Associating an entity with a search query

ABSTRACT

Methods and apparatus for associating an entity with at least one search query. Some implementations are directed to methods and apparatus for identifying multiple queries associated with an entity and identifying one or more of the queries as an entity search query that provides desired search results for the entity. Some implementations are directed to methods and apparatus for identifying a particular entity and, in response to identifying the particular entity, identifying an entity search query corresponding to the particular entity.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation under 35 U.S.C. §120 of U.S. patentapplication Ser. No. 13/801,805, filed Mar. 13, 2013, which is acontinuation of U.S. patent application Ser. No. 13/801,383, filed Mar.13, 2013. The entire disclosures of these applications are incorporatedherein by reference.

BACKGROUND

This specification is directed generally to digital informationretrieval and, particularly to associating an entity with at least onesearch query.

Internet search engines provide information about Internet accessibledocuments such as web pages, images, text documents, and/or multimediacontent. A search engine may identify the documents in response to auser's search query that includes one or more search terms and/orphrases. The search engine ranks the documents based on the relevance ofthe documents to the query and the importance of the documents andprovides search results that link to the identified documents. Thesearch results may be presented to the user in an order that is based onthe rank of the search results. The rank of each search result may bebased on a score assigned to the search result based on one or morescoring functions.

SUMMARY

The present disclosure is directed to methods and apparatus forassociating an entity with at least one search query. For example, someimplementations are directed to methods and apparatus for identifyingmultiple queries associated with an entity and identifying one or moreof the queries as an entity search query that provides desired searchresults for the entity. Also, for example, some implementations aredirected to methods and apparatus for identifying a particular entity(e.g., via a search request for the particular entity) and, in responseto identifying the search request, identifying an entity search querycorresponding to the particular entity.

In some implementations a computer implemented method may be providedthat includes the steps of: receiving a query; identifying an entityassociated with the query; providing an entity summary for the entity todisplay in response to the query, the entity summary includinginformation about the entity and including an option to performadditional searching related to the entity; identifying an entity searchquery associated with the option; and associating the entity searchquery with the selected option.

This method and other implementations of technology disclosed herein mayeach optionally include one or more of the following features.

The entity search query may be associated with the entity and the optionmay be to perform additional searching for the entity. The method mayfurther include the steps of: including a second option to performadditional searching related to the entity; identifying a second entitysearch query associated with the second option; and associating thesecond entity search query with the second option. The second entitysearch query may be associated with a related entity of the entity andthe second option may be to perform additional searching for the relatedentity.

The entity search query may be associated with a related entity of theentity and the option may be to perform additional searching for therelated entity. The method may further include the steps of: including asecond option to perform additional searching related to the entity;identifying a second entity search query associated with the secondoption; and associating the second entity search query with the secondoption, wherein the second entity search query may be associated with asecond related entity of the entity and the second option may be toperform additional searching for the second related entity.

The method may further include the step of issuing a search based on theentity search query in response to selection of the option. The entitysearch query may be identified based on an entity to query mapping. Themethod may further include the step of identifying the entity based on aquery to entity mapping.

Other implementations may include a non-transitory computer readablestorage medium storing instructions executable by a processor to performa method such as one or more of the methods described herein. Yetanother implementation may include a system including memory and one ormore processors operable to execute instructions, stored in the memory,to perform a method such as one or more of the methods described herein.

Particular implementations of the subject matter described hereinanalyze one or more aspects of an entity, queries associated with theentity, and/or documents identified in response to the queriesassociated with the entity to create an association between an entityand one or more queries. These associations represent new aspects ofentities and queries that may be derived from a mapping of queries toentities. The associations may be utilized by one or more applications,such as a search system and/or a query suggestion system, to provideimproved search results to users of the applications.

It should be appreciated that all combinations of the foregoing conceptsand additional concepts discussed in greater detail herein arecontemplated as being part of the inventive subject matter disclosedherein. For example, all combinations of claimed subject matterappearing at the end of this disclosure are contemplated as being partof the inventive subject matter disclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of an example environment in which anentity may be associated with an entity search query; a search query maybe associated with at least one entity; and/or an entity search querymay be identified for a selected entity.

FIGS. 2A and 2B illustrate example graphical user interfaces fordisplaying search results in response to a query; the search resultsinclude entity summaries that may be selected by a user to obtain searchresults specific to an entity.

FIG. 3 is a flow chart illustrating an example method of associating anentity with at least one entity search query.

FIG. 4 is a flow chart illustrating an example method of identifying anentity search query for a user selected entity and issuing a searchbased on the entity search query.

FIG. 5 is a flow chart illustrating an example method of identifying anentity search query for a user selected query suggestion associated withan entity and issuing a search based on the entity search query.

FIG. 6 illustrates an example graphical user interface for displaying aquery suggestion that includes an entity descriptor.

FIG. 7 illustrates a flow chart illustrating an example method ofassociating one or more entities with a query.

FIG. 8 illustrates an example architecture of a computer system.

DETAILED DESCRIPTION

FIG. 1 illustrates a block diagram of an example environment in which anentity may be associated with at least one entity search query; a searchquery may be associated with at least one entity; and/or an entitysearch query may be identified for a selected entity. In someimplementations entities are topics of discourse. In someimplementations, entities are persons, places, concepts, and/or thingsthat can be referred to by a text fragment (e.g., a term or phrase) andare distinguishable from one another (e.g., based on context). Forexample, the text “bush” on a webpage may potentially refer to multipleentities such as President George Herbert Walker Bush, President GeorgeWalker Bush, a shrub, and the rock band Bush. Also, for example, thetext “sting” may refer to the musician Gordon Matthew Thomas Sumner orthe wrestler Steve Borden.

In some implementations an entity may be referenced by a unique entityidentifier that may be used to identify the entity. The unique entityidentifier may be associated with one or more properties associated withthe entity. For example, in some implementations the entity propertiesdatabase 105 may include properties associated with unique identifiersof one or more entities. For example, a unique identifier for the entityassociated with the wrestler Steve Borden may be associated with a nameor alias property of “Sting”, another alias property of “Steve Borden”,an occupation property of “wrestler”, and/or a birthdate property of“Mar. 20, 1959” in the entity properties database 105. Additional and/oralternative properties may be associated with an entity in one or moredatabases such as entity properties database 105. In some examples inthis specification, an entity may be referenced with respect to a uniqueentity identifier. In some examples, the entity may be referenced withrespect to one or more alias and/or other property of the entity.

The example environment of FIG. 1 includes a client device 130, theentity properties database 105, a document and entity associationdatabase 110, a search engine 115, a query to entity association system120, a query to entity association database 125, a query suggestionsystem 135, an entity to query association system 140, and an entity toquery association database 145. The environment also includes acommunication network 101 that enables communication between variouscomponents of the environment. In this specification, the term“database” will be used broadly to refer to any collection of data. Thedata of a database does not need to be structured in any particular way,or structured at all, and it can be stored on storage devices in one ormore locations. Thus, for example, the entity properties database 105may include multiple collections of data, each of which may be organizedand accessed differently.

In some implementations the entity properties database 105 may include adatabase of structured data that includes nodes that represent entitiesand identifies the type of each entity represented by a node. A noderepresenting an entity may also be associated with metadata in thedatabase of structured data (e.g., via links that represent propertiesof the entity). Any included metadata may include, for example,names/aliases for the entity, resource locators of resources that areabout the entity, descriptive information about the entity, among otherdata. Each node in the online database of structured data may beassociated with an entity identifier for the entity that can be used toidentify the entity and that optionally remains constant. For example,if a person represented by a node changes their legal name, a uniqueidentifier for the node representing the person may remain constantwhile the metadata that identifies the person's legal name can bechanged to reflect the change to the person's legal name.

In some implementations the entity properties database 105 may includelinks between nodes and data that identifies the relationship betweenentities represented by linked nodes. An example of an online databaseof structured data that exists is the FREEBASE database. Other sourcesmay include online encyclopedias having pages directed to each of agroup of entities and websites directed to particular types of entities(e.g., actors, directors, producers, politicians, sports stars). Othersources may also include one or more database of structured data that isnot freely accessible online. As discussed herein, in someimplementations the entity properties database 105 may be utilized bythe search system 115, the query to entity association system 120, thequery suggestion system 135, and/or the entity to query associationsystem 140.

The query to entity association database 125 may include an index ofqueries and associated entities. For example, for each query, a mapping(e.g., data defining an association) between the query and one or moreentities related with the query may be identified in the query to entityassociation database 125. In some implementations the query to entityassociation database 125 may be generated by the query to entityassociation system 120 and/or utilizing the method of FIG. 7. The queryto entity association system 120 may include memory for storage of dataand software applications, a processor for accessing data and executingapplications, and components that facilitate communication over acommunication network 101. In some implementations the query to entityassociation database 125 may be generated utilizing alternativeapparatus and/or method. In some implementations the query to entityassociation database 125 may be utilized by the entity to queryassociation system 140, the search system 115, the query suggestionsystem 135, and/or one or more additional and/or alternative components.For example, in some implementations, the search system 115 may identifyone or more entities associated with a received query and provideinformation related to the entity as part of the search results. Forexample, an entity associated with a received search query may beidentified via the query to entity association database 125 and anentity summary that includes information about the entity may beprovided along with the search results. In some implementations thesearch system 115 may perform one or more of the steps of the method ofFIG. 4.

In some implementations one or more aspects of information about theentity may be obtained from the entity properties database 105. Forexample, in some implementations the query to entity associationdatabase 125 may associate only one or more unique entity identifiers ofone or more entities with a given query and one or more properties ofthe entities may be obtained from the entity properties database 105based on the unique entity identifiers. In some implementations one ormore properties of the entity may be obtained from the query to entityassociation database 125 itself. For example, the query to entityassociation database may 125 associate a given entity with one or moreentity properties such as properties to be provided in entity summariesfor that entity.

Also, for example, in some implementations, the query suggestion system135 may identify one or more entities associated with a received queryvia the query to entity association database 125. The query suggestionsystem 135 may provide one or more query suggestions based on theidentified entities, with each of the query suggestions beingparticularly formulated to focus on a particular entity. For example,the musician Gordon Matthew Thomas Sumner and the wrestler Steve Bordenmay be associated with the query “sting” in the query to entityassociation database 125. In response to a received query “sting”, thequery suggestion system 135 may identify the musician Gordon MatthewThomas Sumner as the dominant entity from the query to entityassociation database 125 and suggest an alternative query suggestion tothe user, with the alternative query suggestion being particularlyformulated for the musician Gordon Matthew Thomas Sumner (e.g., “stingmusician”).

Also, for example, the query suggestion system 135 may identify multipleentities associated with a received query via the query to entityassociation database 125 and the query suggestion system 135 may suggestalternative query suggestions based on the identified multiple entities.Each of the alternative query suggestions may be particularly formulatedfor a given of the multiple entities. For example, both the musicianGordon Matthew Thomas Sumner and the wrestler Steve Borden may beassociated with the query “sting” in the query to entity associationdatabase 125. In response to a received query “sting”, the querysuggestion system 135 may identify both the musician Gordon MatthewThomas Sumner and the wrestler Steve Borden from the query to entityassociation database 125 and suggest two alternative query suggestions,with each being particularly formulated for one of the entities. Forexample, the query suggestion system 135 may provide a first querysuggestion of “sting musician” and a second query suggestion of “stingwrestler.”

The query that is actually submitted in response to a user selection ofa query suggestion for an entity may be based on an entity search querythat is associated with that entity. As discussed herein, in someimplementations an entity search query associated with an entity may beobtained via the entity to query association system 140 and/or theentity to query association database 145. The entity to queryassociation system 140 may include memory for storage of data andsoftware applications, a processor for accessing data and executingapplications, and components that facilitate communication over acommunication network 101

The entity to query association database 145 may include an index ofentities and associated entity search queries. For example, for eachentity, a mapping (e.g., data defining an association) between theentity and one or more entity search queries related with the entity maybe identified in the entity to query association database 145. In someimplementations one or more entities of the entity to query associationdatabase 145 may contain only a single entity search query associatedtherewith. For example, in some implementations the single query for anentity may be a query identified as providing desired search results forthat entity. In some implementations the single query may be identifiedas providing desired search results for that entity utilizing the stepsof the method of FIG. 3.

In some implementations one or more entities of the entity to queryassociation database 145 may contain multiple entity search queriesassociated therewith. For example, in some implementations a firstentity search query for an entity may be a query identified asidentifying desired search result documents for the entity for a firstintended application and a second entity search query for the entity maybe identified as identifying desired search result documents for theentity for a second intended application unique from the first intendedapplication. For example, the first intended application may beproviding search results for display for a user and the second intendedapplication may be an entity fact mining application. For example, forthe entity associated with Sting the singer a query “sting musician” maydisplay more popular search results and be associated with the providingsearch results for display application whereas a query “sting gordonsumner” may provide search results more narrowly focused on the entityand be associated with the entity fact mining application. In someimplementations the entity to query association database 145 may beutilized by the entity to query association system 140, the searchsystem 115, the query suggestion system 135, and/or one or moreadditional and/or alternative components.

In some implementations the query suggestion provided by the querysuggestion system 135 and the query actually submitted in response tothe provided query suggestion may differ. For example, if the providedquery suggestion is “sting musician” and the user chooses that querysuggestion, a query of “sting Gordon Sumner” may be submitted to thesearch system 115. In some of those implementations the query of “stingGordon Sumner” may be an entity search query for that entity from entityto query association database 145. In some of those implementations thequery suggestion of “sting musician” may be based on properties fromentity properties database 105 for that entity, such as one or more ofthe most popular properties.

In some implementations the query suggestion system 135 may provide aquery suggestion to a user and, if the user chooses the querysuggestion, may submit a query that strictly conforms to the providedquery suggestion. For example, if the provided query suggestion is“sting musician” and the user chooses that query suggestion, a query of“sting musician” may be submitted to the search system 115. In some ofthose implementations the query suggestion and the query may be anentity search query for that entity from entity to query associationdatabase 145.

In some implementations the query suggestion system 135 may providesuggested queries for display with search results. For example,suggested queries may be provided in combination with search resultssuch as search results of FIGS. 2A-2B. In some implementations the querysuggestion system 135 may provide query suggestions for display inand/or adjacent to a search field. For example, the query suggestionsystem 135 may provide query suggestions as a user is formulating aquery as illustrated, for example, in FIG. 6. In some implementationsthe query suggestion system 135 may perform one or more of the steps ofthe method of FIG. 5.

In some implementations one or more aspects of a provided querysuggestion may be obtained from the entity properties database 105. Forexample, in some implementations the query suggestion system 135 mayassociate only one or more unique entity identifiers of one or moreentities with a given query and one or more properties of the entitiesprovided in a provided query suggestion may be obtained from the entityproperties database 105 based on the unique entity identifiers. Forexample, in response to a received query “sting”, the query suggestionsystem 135 may identify the musician Gordon Matthew Thomas Sumner fromthe query to entity association database 125 and suggest an alternativequery suggestion of “sting musician”. The alternative query suggestionof “sting musician” may be identified based on the entity propertiesdatabase 105. For example, in some implementations properties (e.g.,“musician”) associated with an entity in the entity properties database105 may be ranked and one or more of the highest ranked properties maybe appended to the query to create an alternative query suggestion. Insome implementations one or more aspects of the information about theentity may be obtained from the query to entity association database 125itself.

In some implementations one or more aspects of any search queryassociated with a given entity may be obtained from the entity to queryassociation system 140 and/or the entity to query association database145. The entity to query association system 140 and/or the entity toquery association database 145 may associate each of a plurality ofentities with one or more entity search queries that provide desiredsearch results specific to the entity. For example, the entity to queryassociation database 145 may associate the musician Gordon MatthewThomas Sumner with the entity search query “sting musician”. In someimplementations the provided query suggestion may additionally and/oralternatively be obtained from the entity to query association database145. For example, in some implementations the provided query suggestionmay be the same as the search query submitted in response to userselection of the query suggestion. In some implementations the providedquery suggestion may be obtained from the entity properties database 105and the search query submitted in response to selection of the querysuggestion may be obtained from the entity to query association database145.

The document and entity association database 110 may include an index ofdocuments and associated entities. For example, for each of a pluralityof documents, a mapping (e.g., data defining an association) between thedocument and one or more entities related with the document may beidentified in the document and entity association database 110. Adocument is any data that is associated with a document address.Documents include HTML pages, word processing documents, portabledocument format (PDF) documents, images, video, and feed sources, toname just a few. The documents may include content such as, for example:words, phrases, pictures, etc.; embedded information (such as metainformation and/or hyperlinks); and/or embedded instructions (such asJavaScript scripts).

In some implementations the document and entity association database 110may be accessible to the query to entity association system 120 indetermining associations between a given query and one or more entitiesassociated with the query. For example, in some implementations, thequery to entity association system 120 may associate a given query withan entity based on association of the entity with one or more documentsthat are responsive to a search based on the query. In someimplementations the document and entity association database 110 may beaccessible to the entity to query association system 140 in determiningassociations between a given entity and one or more search queriesassociated with the entity. For example, in some implementations, thequery association system 140 may associate a given entity with a querybased on association of the entity with one or more documents that areresponsive to a search based on the query.

In some implementations an association between a document and an entitymay be based on presence of one or more properties of the entity in thedocument. For example, an association between a document and an entitymay be based on an importance of one or more alias of the entity in thedocument. For example, appearance of an alias of an entity in importantfields and/or with great frequency in a document may be indicative ofassociation of the entity to the document. Also, for example, anassociation between a document and an entity may be based on presence ofadditional and/or alternative properties of an entity such as date ofbirth, place of birth, height, weight, population, geographiclocation(s), type of entity (e.g., person, actor, location, business,university), etc.

In some implementations an association between a document and an entitymay be based on presence in the document of one or more other entitiesrelated the entity. For example, links between entities may beidentified from a database such as entity properties database 105. Forexample, the entity properties database 105 may include spouseinformation for an entity and an association between a document and aperson may be based on occurrence of a spouse of the person in thedocument. For example, if a person's alias is ambiguous, presence of analias of the person's spouse in a document along with the person's aliasmay be more indicative of the person being associated with the documentthan if the person's alias appeared in the document without the alias ofthe person's spouse. Also, for example, an association between adocument and an entity may be based on presence of additional and/oralternative entities associated with a given entity, such as co-workers,co-stars, similar types of businesses, etc. Additional and/oralternative factors may be utilized in associating a document with oneor more entities. Also, for example, an association between a documentand an entity may be identified based on association between that entityand other entities in the document. For example, an entity may beassociated with one or more additional entities based on co-occurrenceof those entities in documents of a corpus of documents and/or based onother identified link such as hyperlinks between a document describingthe entity and another document describing one of the additionalentities. For example, a document may contain the term “Sting” and mayalso contain the term “wrestler”. Based on an association between theentity associated with the wrestler Sting and the entity representingthe concept of wrestling, the entity associated with the wrestler Stingmay be identified as associated with the document.

In some implementations a user may interact with the search system 115through a client computing device 130. The computing device 130 may be,for example, a desktop computer, a laptop computer, a cellular phone, asmartphone, a personal digital assistant (PDA), a tablet computer, anavigation system, or another computing device. The computing device 130and the search system 115 each include memory for storage of data andsoftware applications, a processor for accessing data and executingapplications, and components that facilitate communication over acommunication network 101. The operations performed by the clientcomputing device 130 and/or the search system 115 may be distributedacross multiple computer systems.

The computing device 130 executes one or more applications, such as webbrowsers (e.g., web browser 132), that enable the user to submit queriesto the search system 115. In some implementations queries may besubmitted directly to the search system 115 from the computing device130. In some implementations queries may be submitted from one or moreother components to the search system 115.

The search system 115 is an example of an information retrieval systemin which the systems, components, and techniques described herein may beimplemented and/or with which the systems, components, and techniquesdescribed herein may interface. The search system 115 receives queriesfrom the client device 130 and/or other component (e.g., query to entityassociation system 120 and/or entity to query association system 140)and returns results in response to the queries. For example, in responseto a query from the computing device 130, the search system 115 maytransmit a plurality of search results to be displayed in the webbrowser 132 that is executing on the computing device 130. Each query isa request for information. The query can be, for example, in a text formand/or in other forms such as, for example, audio form and/or imageform. Other computer devices may submit search queries to the searchsystem 115 such as a server implementing a service for a website thathas partnered with the provider of the search system 115. For brevity,however, the examples are described in the context of the client device130, the query to entity association system 120, the entity to queryassociation system 140, and/or the query suggestion system 135.

In some implementations, as described herein, the entity to queryassociation system 140, the query to entity association system 120,and/or the query suggestion system 135 may additionally interact withthe search system 115. For example, as described with respect to themethod of FIG. 3, in some implementations the entity to queryassociation system 140 may interface with the search system 115 inassociating an entity with an entity search query based on the queryscore.

The search system 115 may include an indexing engine and a rankingengine. The indexing engine maintains an index for use by the searchsystem 115. The indexing engine processes documents and updates indexentries in the index, for example, using conventional and/or otherindexing techniques.

The ranking engine uses the index to identify documents responsive to asubmitted query, for example, using conventional and/or otherinformation retrieval techniques. The ranking engine calculates scoresfor the documents responsive to the query, for example, using one ormore ranking signals. Each signal provides information about thedocument itself and/or the relationship between the document and thequery. One example signal is a measure of the overall quality of thedocument. Another example signal is a measure of the number of times theterms of the query occur in the document. Additional and/or alternativesignals can also be used.

For example, additional and/or alternative signals include informationabout the query itself such as, for example, the terms of the query, anidentifier of the user who submitted the query, and/or a categorizationof the user who submitted the query (e.g., the geographic location fromwhere the query was submitted, the language of the user who submittedthe query, interests of the user who submitted the query, and/or a typeof the client device 130 used to submit the query (e.g., mobile device,laptop, desktop)). The identification of the user can be, for example, auser name or the IP address of the client device 130. The geographiclocation from where the query was submitted can be, for example, acontinent, a country, a state, a city, or geographic coordinates, suchas latitude and longitude.

Signals may also include information about the terms of the query suchas, for example, the locations where a query term appears in the title,body, and text of anchors in a document, where a query term appears inanchors pointing to the search result, how a term is used in thedocument (e.g., in the title of the document, in the body of thedocument, or in a link in the document), the term frequency (i.e., thenumber of times the term appears in a corpus of documents in the samelanguage as the query divided by the total number of terms in thecorpus), and/or the document frequency (i.e., the number of documents ina corpus of documents that contain the query term divided by the totalnumber of documents in the corpus).

Further examples of signals include information about the document, forexample, a measure of the quality of the document, a measure of thepopularity of the document, the URL of the document, the geographiclocation where the document is hosted, when the search system 115 firstadded the document to the index database, the language of the document,the size of the document, the length of the title of the document,and/or the length of the text of source anchors for links pointing tothe document.

The ranking engine then ranks the responsive documents using the scores.For example, the responsive documents are ranked based on the scores. Insome implementations information pertaining to one or more of theresponsive documents, the scores of the one or more responsivedocuments, and/or the rankings of the one or more responsive documentsmay be provided to query to entity association system 120 for use inassociating queries with one or more entities and/or the entity to queryassociation system 140 for use in associating a query with one or moreentity search queries. The search system 115 uses the documentsidentified and scored by the ranking engine to generate results. Theresults include results corresponding to documents responsive the query.For example, results can include titles of each of the documents, linksto each of the documents, and/or a summary of content from each of thedocuments that is responsive to the query. For example, the summary ofcontent may include a particular “snippet” or section of one or moredocuments that is responsive to the query.

Other examples of results include a summary of information responsive tothe query. The summary can be generated from documents responsive to thequery and/or from other sources. For example, in some implementationsthe summary can be generated based on identification of one or moreentities associated with a submitted query. For example, in someimplementations the search system 115 may identify an entity associatedwith a query via query to entity association database 125. In responseto the query, results may be provided that include a summary of theentity. For example, the entity and/or one or more properties of theentity may be provided as a result. Also, for example, in someimplementations the search system 115 may identify an entity searchquery for the entity via entity to query association database 145. Theidentified entity search query for the entity may be displayed incombination the search results as an alternative query suggestion and/orassociated with the entity summary to enable searching based on theidentified entity search query (e.g., via selecting a “see results aboutthe entity” link in the entity summary).

The results are transmitted to the client device 130 in a form that maybe provided to the user. For example, the results 130 may be transmittedas a search results web page to be displayed on a browser running on theclient device and/or as one or more search results conveyed to a uservia audio.

The one or more applications executing on the computing device 130 mayadditionally and/or alternatively provide partial queries beingformulated by users, before the users have indicated completion of thequeries. The applications may be, for example, a web browser, a toolbarrunning in a web browser, an e-mail application, a text-messagingapplication, and/or a search client running on the computing device 130.In some implementations the applications provide each character of aquery as it is typed or otherwise entered by the user. In someimplementations the applications provide multiple characters at a time,optionally following a pause by the user between character entries.

A partial query is a query formulated by a user prior to an indicationby the user that the query is a completed query. In some implementationsa user may indicate a completed query by entering a carriage returnand/or other character. In some implementations a user may indicate acompleted query by selecting a search button or other submission buttonin a user interface presented to the user. In some implementations auser may indicate a completed query by speaking a command in a speechuser interface. In some implementations a user may indicate a completedquery by pausing more than a predetermined amount of time duringentering of the query. Other forms of providing a partial query and/orindicating a completed query may additionally and/or alternatively beutilized.

In response to a partial query entered by a user, the computing device130 may facilitate entry of user input by providing suggested inputs tothe user. For example, when the user enters one or more characters, thecomputing device 130 can provide autocomplete query suggestions that areselected using the one or more characters. In some implementations theautocomplete query suggestions may be provided to the computing device130 by query suggestion system 135. The autocomplete query suggestionsthat are provided may include words or phrases that include the one ormore characters that were entered by the user. For example, completewords or extended phrases can be suggested for partial words or partialphrases that a user has entered (e.g., using a physical or virtualkeyboard). The autocomplete query suggestions can also include words orphrases that are similar to (e.g., synonyms or spelling corrections of)the user input. The user can interact with (e.g., tap, click, orotherwise affirmatively select) one of the provided autocomplete querysuggestions to select the autocomplete query suggestion.

In some implementations, the computing device 130 does not initiate asearch using the query in response to a selection of an autocompletequery suggestion. Rather, the computing device 130 can wait to initiatea search until query completion data is received. The query completiondata can indicate that the user has finished composing a complete query.The query completion data can be received as an interaction with a userinterface element that occurs separate from the selection of anautocomplete query suggestion.

The autocomplete query suggestions may be displayed to a user in a userinterface of the computing device 130. For example, the autocompletequery suggestions may be displayed as illustrated in FIG. 6 within acascaded drop down menu of the search field of an application, such as aweb browser executing on the computing device 130, as the user is typingthe query. Also, for example, the autocomplete query suggestions may bedisplayed in a plurality of separately selectable cells arranged in oneor more rows or columns in a user interface as the user is typing thequery. In some implementations one or more search results for a querysuggestion may also optionally be displayed as the user is typing thequery.

In some implementations, in response to a partial query being entered atcomputing device 130, the search system 115 receives the partial queryand forwards the partial query to the query suggestion system 135. Insome implementations, in response to a partial query being entered atcomputing device 130, the one or more applications executing on thecomputing device 130 may optionally directly forward the partial queryto the query suggestion system 135. For example, in some implementationsthe browser 132 may directly forward the partial query to the querysuggestion system 135. The query suggestion system 135 includes memoryfor storage of data and software applications, a processor for accessingdata and executing applications, and components that facilitatecommunication over the communication network 101. The query suggestionsystem 135 may then match the submitted partial query to one or more ofa plurality of autocomplete query suggestions that are an appropriatematch to the partial query. In some implementations the autocompletequery suggestions may represent potential completed queries that may beprovided to a user to enable the user to choose one of the autocompletequery suggestions as a basis for utilization in a search or otherinformation retrieval application.

As discussed herein, in some implementations one or more of the providedautocomplete query suggestions may be determined via the query to entityassociation system 120, the query to entity association database 125,and/or the entity to query association system 140. For example, in someimplementations one or more of the autocomplete query suggestions mayinclude an entity descriptor that is based on an identified entityassociated with the query and/or a query suggestion for the query. Forexample, each of the autocomplete query suggestions for the partialquery “washington” in FIG. 6 is provided with an entity descriptor. Theentity descriptor may be based on identification of one or more entitiesassociated with the autocomplete query suggestion as determined viaquery and entity suggestions system 120 and/or query to entityassociation database 125. In some implementations the autocomplete querysuggestions may include those determined based on a list of past userqueries, a list of automatically generated queries, and/or real timeautomatically generated queries. For example, the query suggestionsystem 135 may use prefix based matching to identify query suggestionsfrom a list of past user queries. Any listing of past user queriesand/or past automatically generated queries may optionally be stored inan autocomplete query suggestion content database, for potentialutilization as query suggestions and/or as a basis for querysuggestions. Any entity annotations of the autocomplete querysuggestions may also optionally be stored and/or determined via query toentity association system 120 and/or query to entity associationdatabase 125.

In some implementations the autocomplete query suggestions may includean entity descriptor that identifies a particular entity associated withthe autocomplete query suggestion. In some implementations the entitydescriptor may be included in a search query submitted in response toselection of the autocomplete suggestion. In some implementations thesubmitted search query may omit the entity descriptor. In someimplementations the provided autocomplete query suggestion and the querysubmitted in response to user selection of the autocomplete querysuggestion may differ. For example, in some implementations a providedautocomplete query suggestion may be identified via query to entityassociation database 125 and the actual query submitted in response toselection of the provided autocomplete query suggestions may beidentified via entity to query association database 145.

In some implementations any provided autocomplete query suggestioncontent database may include one or more autocomplete query suggestionsthat have been determined, scored, and/or sorted according to one ormore methods and/or apparatus described herein. For example, theautocomplete query suggestion content database may include one or moreautocomplete query suggestions that have been determined, scored, and/orsorted based on one or more entities associated with the autocompletequery suggestion and/or one or more entities responsive to a partialquery for which the autocomplete query suggestion is responsive. Forexample, for the partial query “sting” autocomplete query suggestions of“sting wrestler” and/or “sting musician” may be determined, scored,and/or sorted based on identification of association between the query“sting” and entities for the wrestler Sting and the musician Sting.Also, for example, for the partial query “stin” (no “g”) autocompletequery suggestions of “sting wrestler” and/or “sting musician” may bedetermined, scored, annotated and/or sorted based on identification ofassociation between an autocomplete suggestion of “sting” (suggestionfor “stin”) and entities for the wrestler Sting and the musician Sting.

Also, for example, the autocomplete query suggestion content databasemay include an actual query submission associated with each of one ormore of the autocomplete suggestions that have been determined, scored,and/or sorted based on the entity associated with the autocompletesuggestion. For example, the actual query submission associated with theautocomplete query suggestion “sting musician” may be determined,scored, and/or sorted based on identification of association between thequery “sting” and entities for the wrestler Sting and the musicianSting. Also, for example, for the partial query “stin” (no “g”)autocomplete query suggestions of “sting wrestler” and/or “stingmusician” may be determined, scored, annotated and/or sorted based onidentification of association between an autocomplete suggestion of“sting” (suggestion for “stin”) and entities for the wrestler Sting andthe musician Sting.

Such autocomplete query suggestions may be provided to a user. In someimplementations the query suggestion system 135 may provide theautocomplete query suggestions to a user via the search system 115, theentity to query association system 140, the query to entity associationsystem 120, and/or to the computing device 130 directly.

In some implementations the query suggestion system 135 may transmit thedetermined additional autocomplete query suggestions, determined scoresfor one or more of the autocomplete query suggestions, a queryassociated with one or more of the autocomplete suggestions, and/or theranking of the autocomplete query suggestions for storage in a database.In some implementations stored data may optionally be associated with acorresponding query in the database for future retrieval in response toa future autocomplete query suggestion request for the query. In someimplementations the query suggestion system 135 may identify existingautocomplete query suggestions for a given partial query to enabledetermination of additional autocomplete query suggestions and/orannotations for storage in a database for future retrieval. In someimplementations the query suggestion system 135 may supply autocompletequery suggestions associated with an entity and/or one or more queriesassociated with the autocomplete suggestions for a real time query.

In some implementations the query suggestion system 135 providesautocomplete query suggestions to a user. In some implementations thequery suggestion system 135 may provide the autocomplete querysuggestions to a user via the search system 115, the query suggestionsystem 135, and/or to the computing device 130 directly.

In some implementations the search system 115 and/or the computingdevice 130 may optionally additionally or alternatively provide acompleted query to the query suggestion system 135. A completed query isa query that the user has indicated is complete. The autocomplete querysuggestion engine 110 may then match the completed query to one or moreautocomplete query suggestions to determine one or more querysuggestions for the user's completed query. The query suggestion system135 then provides these query suggestions to the user. The querysuggestions may, for example, be embedded within a search results webpage to be displayed in an application, such as the web browser 132, aspotential further search options.

The communication network 101 facilitates communication between thevarious components in the environment. In some implementations thecommunication network 101 may include the Internet, one or moreintranets, and/or one or more bus subsystems. The communication network101 may optionally utilize one or more standard communicationstechnologies, protocols, and/or inter-process communication techniques.

Many other configurations are possible having more or less componentsthan the environment shown in FIG. 1. For example, although the query toentity association system 120, the entity to query association system140, and the search system 115 are each illustrated alone in FIG. 1, itis understood that one or more aspects of two or more of the systems mayoptionally be combined with one another and/or with aspects of one ormore of the other components in some implementations. Also, for example,in some implementations one or more components may be omitted such asquery suggestion system 135, query to entity association system 120,query to entity association database 125, and/or entity propertiesdatabase 105.

FIGS. 2A and 2B illustrate example graphical user interfaces fordisplaying search results in response to a query. The illustratedgraphical user interfaces include one or more entity summariesincorporated therewith. The entity summaries include one or moreproperties of an entity associated with the respective queries. Asdiscussed herein, the properties may be obtained, for example, from theentity properties database 105 and/or the query to entity associationdatabase 125. The entity summaries and/or the properties displayed withthe entity summaries may optionally be ranked utilizing one or moresignals related to the entities, related to the query and/or related toone or more documents responsive to the query. Signals can include, forexample, one or more signals such as those described with respect toFIG. 1. Any optionally determined rankings may be utilized to determinewhich entities are provided in an entity summary, an order of multipleentity summaries, which properties of an entity are provided in anentity summary, and/or an order of multiple properties in an entitysummary.

In FIG. 2A the query “washington” 204A is submitted to a search engine,through the graphical user interface, and a set of search results thatare responsive to the query 204A are generated by the search engine andpresented in the user interface. The search results in FIG. 2A includesearch results 208A that are based on search result documents responsiveto the query. The search results 208A may be ranked according to one ormore signals as discussed herein such as document based signals and/orquery based signals. The search results in FIG. 2A also include anexpanded entity summary 250A for the state of Washington andnon-expanded entity summaries 260A. The non-expanded entity summariesinclude summaries for the entities “Washington D.C.” 261A, the“University of Washington” 262A, and “George Washington” 263A. Theexpanded entity summary 250A includes more information than each of theentity summaries 260A. The entity summary 250A and/or the entitysummaries 261A, 261B, and/or 261C may optionally be selected (e.g., viaclicking or hovering over) to navigate to additional information aboutthe respective entity, to provide a more detailed entity summary on thesearch results page of FIG. 2A (e.g., effectively “expanding” theselected entity summary), and/or to obtain search results that are morefocused toward the selected entity (e.g., via issuing a new searchspecific to that entity and/or filtering the existing search results).

For example, selecting the entity summary 250A may issue a new searchfor the entity associated with “washington state” and search resultsresponsive to that query may be provided. In some implementations thenew search issued for the entity associated with “washington state” maybe based on an entity search query identified via the entity to queryassociation database 145. For example, the entity associated with“washington state” may be mapped to an entity search query in entity toquery association database 145 that provides desired search results to auser that are responsive to that entity. For example, the entityassociated with “washington state” may be mapped to the entity searchquery “state of washington” in the entity to query association database145.

Although specific entity summaries 250A and 260A are illustrated in FIG.2A, it is understood that additional and/or alternative propertiesrelated to an entity may be provided. For example, in someimplementations one or more images of an entity and/or related to anentity may be provided in an entity summary. Also, for example, in someimplementations an entity search query for an entity that is associatedwith the entity in the entity to query association database 145 may bedisplayed in the entity summary. For example, the entity summaryassociated with the entity “washington state” may be mapped to the query“state of washington” in the entity to query association database andthe text of “state of washington” may be provided in the entity summaryas a search that may be issued to obtain search results relevant to theentity “washington state”.

The entities associated with the entity summaries 250A and 260A may beidentified based on association of the query 204A with the entities ofthe entity summaries 250A and 260A. The association may be determinedvia query to entity association system 120 and/or query to entityassociation database 125. In some implementations the entity summaries250A and 260A may be presented based on a ranking of the respectiveentities for the query 204A in the query to entity association database125. For example, the state of Washington may be the highest rankedentity followed in order by “Washington D.C.”, “University ofWashington”, then “George Washington.” In some implementations theexpanded entity summary 250A may be expanded based on it being based onthe highest ranked entity. In some implementations the expanded entitysummary may be expanded based on satisfaction of a threshold relative tothe ranking of a second highest ranked entity such as the entityassociated with “Washington D.C.”.

In some implementations any score and/or ranking associated with theentities of the entity summaries 250A and 260A may be based on scoresassociated with the entities by query to entity association system 120and/or in query to entity association database 125. In someimplementations the ranking of the entities may be adjusted and/ordetermined based on the search result documents associated with searchresults 208A and/or additional search result documents responsive to thequery. For example, in some implementations the entity Washington Statemay be associated with a score for the query “Washington” in the queryto entity association database 125 and the score may be adjusted basedon the results 208A. For example, the score may be boosted based on thetop ranked search result of the search results 208A being aboutWashington State and an additional displayed search result (the lastdisplayed search result) also being about Washington State. Ranking ofthe entities based at least in part on the search results 208A mayenable ranking of the entities based on search results that arepersonalized to the user (e.g., based on user data) and/or to enableranking of the entities based on fresh search results (e.g., to accountfor promotion and/or demotion of search results since any prior rankingwas determined).

In FIG. 2B the query “washington dc” 204B is submitted to a searchengine, through the graphical user interface, and a set of searchresults that are responsive to the query 204B are generated by thesearch engine and presented in the user interface. The search results inFIG. 2B include search results 208B that are based on search resultdocuments responsive to the query 204B. The search results 208B may beranked according to one or more signals as discussed herein such asdocument centric signals and/or query centric signals. The searchresults in FIG. 2B also include an entity summary 250B for “WashingtonD.C.”

The entity summary 250B includes a points of interest listing 270B inwhich additional properties associated with Washington D.C. are listed.The listed properties include additional entities that are associatedwith Washington D.C. (e.g., mapped to Washington D.C. in the entityproperties database 105). The related entities include “The White House”271B, “Smithsonian” 272B, and “Washington Monument” 273B. In someimplementations the related entities may be selected and/or orderedbased on a ranking associated with the related entities. For example,the White House may be the highest ranked entity followed in order bythe Smithsonian then the Washington Monument. In some implementationsthe ranking for properties for an entity, such as related entities, maybe based on a relationship between the property and the query and/or arelationship between the property and the search result documentsassociated with the entity.

For example, in some implementations the points of interest listing 270Bmay be determined based on satisfaction of a threshold. For example, insome implementations where the ranking is based on a score associatedwith the properties and a higher score is associated with a higherranking, the threshold may be satisfied if the score of the propertyexceeds the score of a threshold value. Although a specific entitysummary 250B and points of interest listing 270B are illustrated in FIG.2B, it is understood that additional and/or alternative propertiesrelated to an entity may be provided. For example, in someimplementations one or more images of and/or related to an entity and/orone or more related entities may be provided in an entity summary.

The entity summary 250B may be identified based on association of thequery 204B with the entity of the entity summary 250B. The associationmay be determined via query to entity association system 120 and/orquery to entity association database 125. In some implementations theentity summary 250B may be presented based on a ranking of the one ormore entities for the query 204B.

In some implementations any score and/or ranking associated with theentity of the entity summary 250B and/or the points of interest listing270B associated with the entity summary 250B and 260A may be based onscores associated with the entities and/or the points of interest byquery to entity association system 120 and/or in query to entityassociation database 125. In some implementations the ranking may beadjusted and/or determined based on the search results 208B and/oradditional search results that are based on search result documentsresponsive to the query. Ranking of the entities and/or the points ofinterest for one or more given entities based on the search results 208Bmay enable ranking of the entities based on search results that arepersonalized to the user (e.g., based on user data) and/or to enableranking of the entities based on fresh search results (e.g., to accountfor promotion and/or demotion of search results since any prior rankingwas determined).

In some implementations the related entities “The White House” 271B,“Smithsonian” 272B, and/or “Washington Monument” 273B may be selected(e.g., via a user interface) to obtain search results that are morefocused toward the selected entity to issue a new search specific tothat entity. For example, selecting the entity 271B may issue a newsearch for the entity associated with “The White House” and searchresults responsive to that query may be provided. In someimplementations the new search issued for the entity associated with“The White House” may be based on a query identified via the entity toquery association database 145. For example, the entity associated with“The White House” may be mapped to a query in entity to queryassociation database 145 that provides desired search results to a userthat are responsive to that entity. For example, the entity associatedwith “The White House” may be mapped to the query “The White HouseWashington D.C.” in the entity to query association database.

While FIGS. 2A-2B show example visual displays of search results,presenting search results can include various forms of presentationincluding, for example, displaying search results on a display device,transmitting search results to a user's computer for presentation to theuser, transmitting search results to another device, transmitting soundscorresponding to the search results, providing haptic feedbackcorresponding to the search results, and/or transmitting signalscomprising haptic feedback corresponding to the search results to auser's computer for presentation to the user.

FIG. 3 is a flow chart illustrating an example method of associating anentity with at least one entity search query. Other implementations mayperform the steps in a different order, omit certain steps, and/orperform different and/or additional steps than those illustrated in FIG.3. For convenience, aspects of FIG. 3 will be described with referenceto a system of one or more computers that perform the process. Thesystem may include, for example, the entity to query association system140 and/or the search system 115 of FIG. 1.

At step 300, an entity is identified. In some implementations the entitymay be identified from the query to entity association database 125. Insome implementations the entity may be identified from another sourcesuch as entity properties database 105. In some implementations thequery to entity association database 125 may, for each of one or morequeries, only contain a single entity associated therewith. In someimplementations the single entity associated with a given query may bethe dominant entity associated with the query. For example, for eachquery a single entity may be associated with the query that is thehighest ranking entity for that query based on one or more signals suchas, for example an entity score for the given entity for the givenquery. In some implementations the query to entity association database125 may contain a mapping of one or more queries that each have multipleentities associated therewith and the entity to query association system140 may reduce the mapping by associating, for each query, only a singledominant entity therewith. For example, the query to entity associationdatabase 125 may contain a mapping of one or more queries that each havemultiple ranked entities associated therewith and the entity to queryassociation system 140 may generate a reduced mapping that only includesqueries with each query mapped to a single highest ranked entityassociated therewith. In some implementations the entity may beidentified from entities of such a reduced mapping.

At step 305, search queries are identified for the entity received atstep 300. In some implementations the entity to query association system140 may identify the search queries based on a mapping of queries toentities such as query to entity association database 125 and/or areduced mapping of query to entity association database 125 as describeabove with respect to step 300. In some implementations the entity toquery association system 140 may invert the mapping of queries toentities to obtain a mapping of entities to queries. A plurality of theentities in the inverted mapping will each have multiple queriesassociated with the entity. In some implementations all of the searchqueries associated with the entity received at step 300 are identified.In some implementations less than all of the search queries areidentified for the entity received at step 300. For example, somethresholding may be utilized to omit certain queries based on one ormore signals related to the queries. For example, queries may be omittedif they fail to satisfy a threshold popularity measure.

At step 310, a query score for each of the identified search queries isidentified. In some implementations the query score for a given searchquery for the entity may be based on one or more of entity ambiguity ofthe query, popularity of the search query, and search result documentquality for the search result documents responsive to the query that areassociated with the entity.

The entity ambiguity of a given query for the identified entity at step300 may be indicative of how related the query is to the identifiedentity. In implementations where a higher query score is more indicativeof association between an entity and a query, the more related a givenquery is to the identified entity, the higher the query score for thegiven entity will be. In some implementations the entity ambiguity maybe based on the query to entity association database 125. For example,in some implementations the query to entity association database 125 maycontain an entity ambiguity measure for one or more entity of one ormore of the queries identified at step 310. For example, an entity scorefor the entity identified at step 300 may be identified for a givenquery of the queries identified at step 305 and utilized to determinethe entity ambiguity of the query.

Also, for example, for a given query of the queries identified at step305, one or more other entities and/or entity scores of other entitiesmapped to the given query in the query to entity database 125 may beutilized to determine entity ambiguity of the query for the identifiedentity. For example, for a given query an entity score for the entityidentified at step 300 may be identified for the given query andcompared to one or more entity scores of other entities mapped to thegiven query in the query to entity to determine entity ambiguity of thequery for the given entity. For example, assuming a difference betweenthe entity score of the entity identified at step 300 and the nexthighest scored entity may be determined and utilized to determine entityambiguity of the query for the identified entity. For example, assumingentity scores from 0 to 1, with 1 being most indicative of relation ofthe query to the entity, a score of 0.6 for the entity identified atstep 300 and an entity score of 0.1 for the next highest scored entitywould be indicative of less entity ambiguity for the identified entitythan if the entity score for the next highest ranked entity was 0.4. Insome implementations entity scores for one or more of the entitiesassociated with the query may be determined by entity to queryassociation system 140. For example, the entity to query associationsystem may perform one or more steps of the method of FIG. 7, such asthose described with respect to step 720, in determining an entityscore.

Also, for example, for a given query for the entity identified at step300 a number of additional entities also associated with the query maybe identified to determine entity ambiguity of the query for theidentified entity. For example, the query may be identified as beingmore related to the entity if only one additional entity is associatedwith the query than if five additional entities were associated with thequery. Also, for example, the query may be identified as being morerelated to the identified entity if only one additional entity having anentity score above a threshold is associated with the query than if fiveadditional entities having the entity score above the threshold areassociated with the query. In some implementations entity ambiguity ofthe query for an identified entity may be based on both a number ofadditional entities also associated with the query and entity scores ofother entities mapped to the given query.

In some implementations the entity ambiguity for a given query for anentity identified at step 300 may additionally and/or alternatively bebased on a relationship between the identified entity and search resultdocuments associated with the query. For example, in someimplementations the entity to query association system 140 may identifywhich of a set of the search result documents responsive to the queryare associated with the identified entity and/or primarily associatedwith the identified entity. For example, if 80% of the top 20 searchresult documents responsive to the query are primarily associated withthe identified entity, the query may be identified as being more relatedto the entity than if only 50% of the top 20 search result documentsresponsive to the query are primarily associated with the identifiedentity. Also, for example, if 80% of the top 20 search result documentsresponsive to the query associate the entity as one of the top twoentities in the documents, the query may be identified as being morerelated to the identified entity than if only 50% of the top 20 searchresult documents responsive to the query as one of the top two entitiesin the documents.

In some implementations the entity to query association system 140 mayidentify whether an entity is associated with a search result documentbased on a database of documents and associated entities such asdocument and entity association database 110. For example, for each ofthe identified search result documents, the document and entityassociation database 110 may be consulted to identify one or moreentities associated with the document. In some implementations anassociation between a document and an entity may be based on presence ofone or more properties of the entity in the document. For example, anassociation between a document and an entity may be based on animportance of one or more alias of the entity in the document. Forexample, appearance of an alias of an entity in important fields and/orwith great frequency in a document may be indicative of association ofthe entity to the document. Also, for example, an association between adocument and an entity may be based on presence of additional and/oralternative properties of an entity such as date of birth, place ofbirth, height, weight, population, geographic location(s), type ofentity (e.g., person, actor, location, business, university), etc. Insome implementations an entity to document ranking for each of multipleentities associated with a search result document may also beidentified. For example, in some implementations the document and entityassociation database 110 may include a ranking and/or score of theentities associated with a given document. For example, the document andentity association database 110 may identify the ranking of each of aplurality of relative entities to one another in a given document.

In some implementations the entity to query association system 140 mayidentify an association between the identified entity and the searchresult documents associated with the entity without accessing a databaseof documents and associated entities. For example, in someimplementations an entity to document association and/or entity todocument ranking may be determined by the entity to query associationsystem 140 and based on frequency of appearance, location of appearance,and/or formatting applied to one or more occurrences of the entity inthe document; frequency of appearance, location of appearance, and/orformatting applied to one or more properties of the entity in thedocument; and/or other factors. Additional and/or alternative factorsmay be considered in determining entity ambiguity of a given query forthe identified entity.

The popularity of a given search query may be indicative of a frequencyof submission of the search query. In implementations where a higherquery score is more indicative of association between an entity and aquery, the more popular a given query is, the higher the query score forthe given entity will be. In some implementations the popularity of agiven query may be based on a query popularity database that associateseach of a plurality of queries with a corresponding popularity score. Insome implementations the popularity of a given query may be based onfrequency of the given query in one or more search logs. Additionaland/or alternative factors may be considered in determining thepopularity of the query.

The search result document quality for the search result documentsresponsive to the query that are associated with the identified entitymay be indicative of the quality of one or more of the search resultsthat are associated with the identified entity. In implementations wherea higher query score is more indicative of association between an entityand a query, the higher the search result document quality for thesearch result documents is, the higher the query score for the givenentity will be. As discussed herein, association between a search resultdocument and a given entity may be based on, for example, a document toentity database and/or determination by entity to query associationsystem 140. The search result document quality for a given search resultmay be based on one or more ranking signals such as one or more rankingsignals described herein with respect to search system 115. For example,the search result document quality for the search result documentsresponsive to the query may be based on the number of users thatnavigate to the search result documents when they are presented assearch results. In some implementations the search system 115 mayprovide the ranking signals.

In some implementations the search result document quality is determinedfor those search result documents that are primarily associated with theidentified entity (e.g., as identified via document and entityassociation database 110). In some implementations the search resultdocument quality is determined for those search result documents whereinthe identified entity is one of the top X ranked entities associatedwith the document, wherein X is an integer. In some implementations thesearch result document quality may be determined for all search resultdocuments that are responsive to the query and associated with theidentified entity. In some implementations the search result documentquality may be determined for a subset of the search result documentsthat are responsive to the query and associated with the entity (e.g.,those of the first 20 search result documents responsive to the queryand identified with the entity). Additional and/or alternative factorsmay be considered in determining search result document quality of thequery.

In some implementations the search result document quality may bedetermined by summing individual search result document quality scoresfor each of those search result documents that are associated with theidentified entity. In some implementations the search result documentquality may be determined by averaging the individual search resultdocument quality scores for each of those search result documents thatare associated with the entity. Additional and/or alternative methodsmay be utilized in determining the search result document quality.

In some implementations the query score for a given search query for theentity identified at step 300 may additionally be based on a similaritymeasure between the given search query and the identified entity. Inimplementations where a higher query score is more indicative ofassociation between an entity and a query, the more similar a givenquery is to the entity, the higher the query score for the given entitywill be. For example, in some implementations the query score for agiven search query for the identified entity may be based on similaritybetween a trusted alias of the identified entity and the search query.For example, the similarity measure may be based on the edit distancebetween the trusted alias of the identified entity and the search query.

The query score for a given search query for the identified entity maybe based on a combination of one or more of the entity ambiguity of thequery, the popularity of the search query, the search result documentquality for the search result documents responsive to the query that areassociated with the identified entity, and the similarity measurebetween the given search query and the identified entity.

In some implementations the weighting of one or more of the entityambiguity of the query, the popularity of the search query, the searchresult document quality for the search result documents responsive tothe query that are associated with the identified entity, and thesimilarity measure between the given search query and the identifiedentity in determining the query score may be based on an intendedapplication of the query to be associated with the entity.

For example, if the query is going to be displayed to a user, then thesimilarity measure between the given search query and the identifiedentity may be weighted more heavily relative to one or more otherfactors to identify a query that a user is likely to associate with thegiven entity when the query is displayed. Also, for example, if thequery is going to be displayed to a user, then the popularity of thesearch query may be weighted more heavily relative to one or more otherfactors to identify a query that may look more natural to a user basedon multiple users having selected the query in the past.

Also, for example, if search results based on the query are going to bedisplayed to a user, then the search result document quality for thesearch result documents responsive to the query may be weighted moreheavily relative to one or more other factors to identify a query thatis likely to provide popular search results for the identified entity tothe user.

Also, for example, if the query is going to be utilized to mine factsabout the identified entity, then the entity ambiguity may be weightedmore heavily relative to one or more other factors to identify a querythat is likely to provide search results that are primarily about theidentified entity.

At step 315 one or more of the search queries identified at step 305 isassociated with the entity identified at step 300 based on the queryscores identified at step 310. For example, for each of the searchqueries identified at step 305, a query score may be determined at step310, and the query associated with the highest query score associatedwith the entity identified at step 300. Also, for example, for each ofthe search queries identified at step 305, a query score may bedetermined at step 310 for each of multiple intended applications, andthe query associated with the highest query score for a first intendedapplication may be associated with the entity identified at step 300 forthe first intended application and the query associated with the highestquery score for the second intended application may be associated withthe entity identified at step 300 for the second intended application.For example, a given entity may be associated with a first query for afirst intended application where the query will be displayed to a user,may be associated with a second query for a second intended applicationwhere search results based on the query will be displayed to a user,and/or may be associated with a third intended application where thequery is going to be utilized to mine facts about the identified entity.In some implementations the association between one or more of thesearch queries identified at step 305 is associated with the entityidentified at step 300 and stored in a database such as entity to queryassociation database 145.

FIG. 4 is a flow chart illustrating an example method of identifying anentity search query for a user selected entity and issuing a searchbased on the entity search query. Other implementations may perform thesteps in a different order, omit certain steps, and/or perform differentand/or additional steps than those illustrated in FIG. 4. Forconvenience, aspects of FIG. 4 will be described with reference to asystem of one or more computers that perform the process. The system mayinclude, for example, the search system 115 and/or the entity to queryassociation system 140 of FIG. 1.

At step 400, a selection to perform a search for an entity isidentified. In some implementations the query may be a query submittedby a user. In some implementations the selection may be received inresponse to a user requesting additional search results about aparticular entity. For example, in some implementations the userselection may be received in response to a user requesting additionalsearch results about an entity displayed in an entity summary, such asone or more of the entity summaries of FIGS. 2A and 2B. In someimplementations the search system 115 and/or the entity to queryassociation system 140 may receive the query. In some implementationsthe query may be a query submitted by another component, such as a factmining system. In some implementations an intended application of thesearch for the entity may also be identified. For example, in someimplementations an intended application of the search for the entity maybe based on a source of the selection to perform the search of for theentity and/or may be explicitly indicated in a received search.

At step 405, an entity search query for the entity is identified. Insome implementations the entity search query may be identified fromentity to query association database 145. In some implementations theentity search query may be identified via entity to query associationsystem 140 performing one or more steps of the method of FIG. 3 such assteps 300-315. In some implementations the entity search query may beidentified based on any intended application of the search for theentity optionally identified at step 400. For example, the identifiedentity search query may be a first search query for a first intendedapplication and a second search query for a second intended application.In some implementations step 405 may be performed before step 400. Forexample, in some implementations an entity search query may beidentified for an entity of the given entity summary prior to selectionto perform a search for the entity via the entity summary. For example,an “obtain additional search results related to entity” link of theentity summary may be associated with the entity search query via step405 and user selection to perform the search via step 400 may includeselecting the link of the entity summary.

At step 410, a search is issued for the entity based on the entitysearch query. For example, the entity search query may be submitted tothe search system 115. In some implementations the entity to queryassociation system 140 may submit the entity search query to the searchsystem 115.

FIG. 5 is a flow chart illustrating an example method of identifying anentity search query for a user selected entity and issuing a searchbased on the entity search query. For convenience, aspects of FIG. 5will be described with reference to a system of one or more computersthat perform the process. The system may include, for example, the querysuggestion system 135 and/or the entity to query association system 120of FIG. 1.

At step 500 a user selection of a query suggestion associated with anentity is identified. For example, with reference to FIG. 6, the query“washington” may be received in the search field 600 and multiple querysuggestions provided in a cascaded drop down menu 620, with one or moreof the query suggestions being associated with an entity. The querysuggestions include: a first query suggestion of “Washington—U.S. Statein Pacific Northwest” that is associated with a first entity andincludes the descriptor “U.S. State in Pacific Northwest”; a secondquery suggestion of “Washington dc—District of Columbia” that isassociate with a second entity and includes the descriptor “District ofColumbia”; a third query suggestion of “Washington (university of)” thatis associated with a third entity includes the descriptor “universityof”; and a fourth query suggestion of “George Washington—1^(st)President” that is associated with a fourth entity and includes thedescriptor “1^(st) President”. At step 500, a user selection of one ofthose query suggestions associated with an entity may be identified. Insome implementations step 505 may be performed before step 500. Forexample, in some implementations an entity search query may beidentified for a given query suggestion associated with a single entityprior to presenting the query suggestion to the user. For example, insome implementations query suggestion system 135 may identify a querysuggestion that is primarily associated with a given entity (e.g., viaan entity annotation and/or via consultation of query to entityassociation database 125) and associate an entity search query with thatquery suggestion (e.g., via consultation of entity to query associationdatabase) prior to presenting the query suggestion to the user to enableuser selection of the query suggestion. In some implementations step 500and step 400 may share one or more aspects in common.

At step 505, an entity search query for the entity associated with thequery suggestion is identified. In some implementations the entitysearch query may be identified from entity to query association database145. In some implementations the entity search query may be identifiedvia entity to query association system 140 performing one or more stepsof the method of FIG. 3 such as steps 300-315. In some implementationsthe entity search query may be identified based on an intendedpresenting search results to a user application of the query. In someimplementations step 505 and step 405 may share one or more aspects incommon.

At step 510, a search is issued for the entity based on the entitysearch query. For example, the entity search query may be submitted tothe search system 515. In some implementations the entity to queryassociation system 540 may submit the entity search query to the searchsystem 515. In some implementations step 510 and step 410 may share oneor more aspects in common.

FIG. 6 illustrates an example graphical user interface for displaying aquery suggestion that includes an entity descriptor. In FIG. 6 theentered query is “washington” and that query and autocompletesuggestions based on that query (washington dc, George washington) areannotated with descriptions of entities. In some implementationsentities may be determined for one or more autocomplete suggestions foran entered query. For example, assume a user entered “washingt” insearch field 600. At step 505 a plurality of entities may be identifiedbased on the term “washingt” by identifying an autocomplete suggestionfor that word such as “washington”, then identifying entities associatedwith that autocomplete suggestion. The autocomplete suggestion“washington” may then be annotated with disambiguating information basedon identification of the multiple entities. For example, entitydescriptors may be provided with “washington” to create querysuggestions of “washington, district of Columbia”, “washington, state inPacific Northwest.” As discussed with respect to FIG. 5, user selectionof one of the autocomplete suggestion from the drop down menu 620 mayresult in a search query being issued for the entity associated with theautocomplete query suggestion. The search query for the entity may beidentified from entity to query association database 145 and mayoptionally be associated with the entity and/or query suggestion priorto storage in query association database 145.

Alternative formats of presenting query suggestions may be provided. Forexample, as discussed herein query suggestions for a submitted query maybe provided in combination with search results for the submitted query.

FIG. 7 is a flow chart illustrating an example method of associating oneor more entities with a query. Other implementations may perform thesteps in a different order, omit certain steps, and/or perform differentand/or additional steps than those illustrated in FIG. 7. Forconvenience, aspects of FIG. 7 will be described with reference to asystem of one or more computers that perform the process. The system mayinclude, for example, the query to entity association system 120 and/orthe search system 115 of FIG. 1.

At step 700, a query is identified. In some implementations the searchsystem 115 may receive the query. In some implementations the query toentity association system 120 may receive the query. In someimplementations the query may be a query submitted by a user. In someimplementations the query may be a query from a log of queries, such asa log of past user queries and/or automatically generated queries.

At step 705, search result documents are identified based on the queryreceived at step 700. For example, in some implementations the query toentity association system 120 may submit the query to the search system115. The ranking engine of the search system 115 may use the index toidentify documents responsive to the query. In some implementations alldocuments identified by the ranking engine of the search system 115 maybe identified at step 705. In some implementations only a subset ofdocuments identified by the ranking engine may be identified at step705. For example, in some implementations only a certain percent of thetotal documents may be identified and/or only a certain number ofdocuments may be identified. For example, in some implementations only acertain percent of the documents having the highest ranking may beidentified. Ranking may be based on, for example, one or more signalsdescribed herein such as document based signals and/or query basedsignals.

At step 710, entities associated with each of the identified searchresult documents are identified. For example, in some implementationsthe query to entity association system 120 may identify the entitiesbased on a database of documents and associated entities such asdocument and entity association database 110. For example, for each ofthe identified search result documents, the document and entityassociation database 110 may be consulted to identify one or moreentities associated with the document. In some implementations anassociation between a document and an entity may be based on presence ofone or more properties of the entity in the document.

One or more of the documents identified in step 700 may be associatedwith one or more entities. In some implementations some of the documentsidentified in step 700 may not be associated with any entities. In someimplementations all entities associated with a document may beidentified. In some implementations only a certain portion of theentities associated with a document may be identified. For example, insome implementations the entities associated with a document may beranked and only one or more of the top ranked entities may beidentified. In some implementations only those entities that satisfy anassociation threshold with the identified search result documents areidentified. For example, in some implementations only those entitiesthat are associated with a threshold number of the search resultdocuments are identified. Also, for example, in some implementationsonly those entities that occur in at least a threshold percentage ofsearch result documents are identified.

At step 715 one or more of the entities is associated with the queryidentified at step 700. In some implementations a given entity isassociated with the query if it can be considered an interpretation ofthe query. Determination of whether a given entity is an interpretationof a query may be based on one or more properties of the entity. In someimplementations the properties may be identified from one or moredatabases such as entity properties database 105.

In some implementations a given entity may be determined to beassociated with the query if it can be considered to satisfy one or moreconditions. For example, a given entity may be determined to beassociated with the query if it can be considered to satisfy one or moreof the following conditions:

-   -   a. The query exactly matches one trusted alias of the entity        (e.g., query “sting” matches a trusted name for the entity        associated with Steven Borden).    -   b. The query contains only one trusted alias of the entity and        additional terms from a list of stop terms and/or stop phrases        (e.g., “who is”, “the”, “an”).    -   c. The query contains only a trusted alias of the entity and a        suffix that represents a property of the entity such as a “type”        of the entity (e.g., “sting wrestler”, “sting musician”, or        “washington state”).    -   d. The query contains one trusted alias of the entity and        additionally, one of the top search result documents for the        query is a reference page for that entity. Top search results        may include, for example, the top X search results, the first        page of search results, only the top search result, etc. The        reference page for that entity may be a webpage that is        referenced as a reference page for the entity in a database such        as entity properties database 105. In some implementations the        reference page for the entity may be a webpage in an online        resource (e.g., one or more white listed resource websites) that        is specifically directed toward that entity.    -   e. The query contains only the name of two entities and/or stop        terms or stop phrases, wherein one of the two entities is        “implied” by the other entity. For example:        -   i. The first entity is a location and the name of one of its            containing locations is the second entity (e.g., “lake tahoe            ca”)        -   ii. The first entity is a media piece such as a book and the            second entity is a creator of the media piece such as an            author (e.g., “da vinci code dan brown”).

In some implementations additional and/or alternative conditions may beutilized in determining whether a given entity is an interpretation of aquery. In some implementations some stemming, spell correction, and/orother textual modification of a received query may be performed prior todetermining whether a given entity is an interpretation of a query. Forexample, a received query of “da venci code dan brown” may be spellcorrected to “da vinci code dan brown”.

At step 720 a ranking is determined for each of the entities associatedwith the query at step 715. In some implementations the ranking is basedon an entity score determined for each of the identified entities. Insome implementations the entity score for a given entity is based on arelationship between the query identified at step 700 and the searchresult documents associated with the given entity. For example, theentity score for a given entity may be based on a query to documentrelevance scores for each of the one or more search result documentsassociated with the given entity. In some implementations the query todocument relevance score for a given document may be based on one ormore signals such as those described herein with respect to the searchsystem 115. Each signal may provide information about the documentitself and/or the relationship between the document and the query. Oneexample signal for a document for a query is the fraction of clicks forthat query going to that document. Another example signal is a measureof the overall quality of the document. In some implementations thequery to document score may be identified by the search system 115.

The query to document relevance scores for each of the documentsassociated with the entity may be utilized in determining a score forthe entity. For example, an entity E₁ may be associated with searchresult documents D₁, D₂, and D₃ and the entity score for entity E₁ maybe based on scores related to relevance of the search result documentsD₁, D₂, and D₃ to the query. For example, the entity score for entity E₁may be based on summing the scores for the documents and/or averagingthe scores for the documents.

In some implementations the entity score for an entity is additionallyand/or alternatively based on a relationship between the entity and thesearch result documents associated with the entity. For example, in someimplementations the query to entity association system 120 may identifya relationship between the entity and the search result documentsassociated with the entity based on a database of documents andassociated entities such as document and entity association database110. For example, for each of the identified documents, the document andentity association database 110 may be consulted to identify a rankingfor one or more entities associated with the document. For example, thedocument and entity association database 110 may include entity todocument relevance scores for each entity in each document. Each entityto document relevance score for a given entity in a given document maybe indicative of the importance of the given entity in the givendocument.

In some implementations the query to entity association system 120 mayidentify a ranking between the entity and the search result documentsassociated with the entity without accessing a database of documents andassociated entities. For example, in some implementations an entity todocument relevance score may be determined by the query to entityassociation system 120 and based on frequency of appearance, location ofappearance, and/or formatting applied to one or more occurrences of theentity in the document; frequency of appearance, location of appearance,and/or formatting applied to one or more properties of the entity in thedocument; and/or other factors.

Additional and/or alternative factors may be considered in determiningan entity to document relevance score. For example, the query to entityassociation system 120 may obtain data that characterizes portions ofthe text of the documents as boilerplate content, (e.g., content that isreused in multiple resources). If the occurrence of the entity is in aportion of the text that has been characterized as boilerplate, theweight of the occurrence in that document can be decreased (e.g., sothat an occurrence in a portion of the text that has been characterizedas boilerplate has a lower weight than an occurrence in a portion of thetext not characterized as boilerplate). Also, for example, in someimplementations, the system also considers occurrences of aliases forthe entity that are not in the text of the resource. For example, thesystem can consider how frequently an alias for the entity occurs in theresource locator (e.g., a Uniform Resource Locator (URL)) for theresource, how frequently an alias for the entity appears in anchor textfor links pointing to the document, and/or how frequently an alias forthe entity appears in the text of search queries submitted to a searchengine that resulted in a user navigating to the document by selecting asearch result identifying the document. One or more of these occurrencescan be given an increased weight, e.g., so that they have a greaterweight than occurrences in the body of the resource.

Another example factor that can be considered is the connectedness ofthe entity to the other entities referred to by aliases in the resource.For example, a connectedness score for an entity can be computed basedon link scores between the entity and each other entity referred to inthe resource. For example, link scores between entities may be obtainedfrom a database such as entity properties database 105.

In some implementations, once the entity to document relevance score foreach entity in a given document have been determined, the entity todocument relevance scores across the entities may be normalized (e.g.,so that the entity to document relevance scores are reduced if theremany different entities referenced in the resource).

The entity to document relevance scores for each of the documentsassociated with the entity may be utilized in determining a score forthe entity. For example, an entity E₁ may be associated with searchresult documents D₁, D₂, and D₃ and the entity score for entity E₁ maybe based on scores related to the relevance of the search resultdocuments D₁, D₂, and D₃ to the entity. For example, the entity todocument relevance score for entity E₁ may be based on summing thescores for the documents and/or averaging the scores for the documents.In some implementations the entity to document relevance scores for agiven entity may be a number from zero to one.

In some implementations the entity score for an entity is based on arelationship between the query and the search result documentsassociated with the entity and is based on a relationship between theentity and the search result documents associated with the entity. Forexample, in some implementations the entity score for an entity isobtained by summing the product of the query to document relevance scoretimes the entity to document relevance scores over all documentscontaining the entity.

For example, an entity E₁ may be associated with search result documentsD₁, D₂, and D₃ and query to document relevance scores of QD₁, QD₂, andQD₃ may be obtained for those search result documents and entity todocument relevance scores of ED₁, ED₂, and ED₃ may be obtained for thosesearch result documents. The entity score for the entity E₁ may be(QD₁*ED₁)+(QD₂*ED₂)+(QD₃*ED₃).

Additional and/or alternative calculations of an entity score may beutilized. In some implementations those additional and/or alternativecalculations may be based on both the query to document relevance scoresand the entity to document relevance scores over one or more documentsresponsive to the query identified at step 700.

In some implementations a highest ranked entity of the entities for aquery may be identified as a dominant entity for that query when theranking of the highest ranked entity satisfies a threshold, such as athreshold relative to the ranking of a lower ranked entity of theentities. For example, if an entity score for a highest ranked entity ofthe entities satisfies a threshold relative to the ranking of a lowerranked entity of the entities (e.g., the second highest ranked entity),then it may be identified as a dominant entity for that query.

In some implementations one or more entities associated with the queryat step 715 may be removed from being associated with the query based onthe ranking determined at step 720. For example, in implementationswhere a score is assigned to the entities, an entity may be removed frombeing associated with the query when the score for that entity fails tosatisfy a threshold. Also, for example, in some implementations only thetop X ranked entities may be associated with a given query (where Xrepresents an integer), wherein those entities that are not in the top Xranked entities are removed from being associated with the query.

In some implementations the association between query received at step700 and the entities associated with the query at step 715 may be storedin a database such as query to entity association database 125. In someimplementations whether an entity is associated with a given query mayalso be based on the ranking for that entity as determined in step 720.For example, in some implementations even though an entity may beconsidered a valid interpretation of a query, it may not be stored inthe query to entity association database 125 if its ranking fails tosatisfy a threshold ranking (e.g., it does not have a score thatsatisfies a threshold, it is ranked too low relative to other entities).

In some implementation the ranking for each of the entities determinedat step 720 may also be stored in a database such as query to entityassociation database 125. For example, in implementations where entityscores are determined for each of the entities associated with thequery, the entity score for each entity for a given query may be storedin the database. For example, for the query “sting” the entityassociated with the wrestler may have a first score and the entityassociated with the singer may have a second score. Also, for example,each entity for a given query may be identified as the primary,secondary, tertiary, etc. entity for the given query in the database.For example, for the query “sting” the entity associated with thewrestler may be identified as the secondary entity and the entityassociated with the singer may be identified as the primary entity.

In some implementations a reduced mapping between queries and entitiesmay be stored in a database such as query to entity association database125 by filtering out any queries that do not have any entitiesassociated therewith (or only have entities that fail to satisfy athreshold ranking). Any stored data may optionally be associated with acorresponding query in the database for future retrieval in response toa future search request for the query.

FIG. 8 is a block diagram of an example computer system 810. Computersystem 810 typically includes at least one processor 814 whichcommunicates with a number of peripheral devices via bus subsystem 812.These peripheral devices may include a storage subsystem 824, including,for example, a memory subsystem 825 and a file storage subsystem 826,user interface input devices 822, user interface output devices 820, anda network interface subsystem 816. The input and output devices allowuser interaction with computer system 810. Network interface subsystem816 provides an interface to outside networks and is coupled tocorresponding interface devices in other computer systems.

User interface input devices 822 may include a keyboard, pointingdevices such as a mouse, trackball, touchpad, or graphics tablet, ascanner, a touchscreen incorporated into the display, audio inputdevices such as voice recognition systems, microphones, and/or othertypes of input devices. In general, use of the term “input device” isintended to include all possible types of devices and ways to inputinformation into computer system 810 or onto a communication network.

User interface output devices 820 may include a display subsystem, aprinter, a fax machine, or non-visual displays such as audio outputdevices. The display subsystem may include a cathode ray tube (CRT), aflat-panel device such as a liquid crystal display (LCD), a projectiondevice, or some other mechanism for creating a visible image. Thedisplay subsystem may also provide non-visual display such as via audiooutput devices. In general, use of the term “output device” is intendedto include all possible types of devices and ways to output informationfrom computer system 810 to the user or to another machine or computersystem.

Storage subsystem 824 stores programming and data constructs thatprovide the functionality of some or all of the modules describedherein. For example, the storage subsystem 824 may include the logic toassociate an entity with at least one entity search query; identify anentity search query for an entity; associate a query with at least oneentity; provide one or more entity summaries for a query; and/oridentify a query suggestion based on a query to entity association.

These software modules are generally executed by processor 814 alone orin combination with other processors. Memory 825 used in the storagesubsystem can include a number of memories including a main randomaccess memory (RAM) 830 for storage of instructions and data duringprogram execution and a read only memory (ROM) 832 in which fixedinstructions are stored. A file storage subsystem 824 can providepersistent storage for program and data files, and may include a harddisk drive, a floppy disk drive along with associated removable media, aCD-ROM drive, an optical drive, or removable media cartridges. Themodules implementing the functionality of certain implementations may bestored by file storage subsystem 824 in the storage subsystem 824, or inother machines accessible by the processor(s) 814.

Bus subsystem 812 provides a mechanism for letting the variouscomponents and subsystems of computer system 810 communicate with eachother as intended. Although bus subsystem 812 is shown schematically asa single bus, alternative implementations of the bus subsystem may usemultiple busses.

Computer system 810 can be of varying types including a workstation,server, computing cluster, blade server, server farm, or any other dataprocessing system or computing device. Due to the ever-changing natureof computers and networks, the description of computer system 810depicted in FIG. 8 is intended only as a specific example for purposesof illustrating some implementations. Many other configurations ofcomputer system 810 are possible having more or fewer components thanthe computer system depicted in FIG. 8.

While several inventive implementations have been described andillustrated herein, those of ordinary skill in the art will readilyenvision a variety of other means and/or structures for performing thefunction and/or obtaining the results and/or one or more of theadvantages described herein, and each of such variations and/ormodifications is deemed to be within the scope of the inventiveimplementations described herein. More generally, those skilled in theart will readily appreciate that all parameters, dimensions, materials,and configurations described herein are meant to be exemplary and thatthe actual parameters, dimensions, materials, and/or configurations willdepend upon the specific application or applications for which theinventive teachings is/are used. Those skilled in the art willrecognize, or be able to ascertain using no more than routineexperimentation, many equivalents to the specific inventiveimplementations described herein. It is, therefore, to be understoodthat the foregoing implementations are presented by way of example onlyand that, within the scope of the appended claims and equivalentsthereto, inventive implementations may be practiced otherwise than asspecifically described and claimed. Inventive implementations of thepresent disclosure are directed to each individual feature, system,article, material, kit, and/or method described herein. In addition, anycombination of two or more such features, systems, articles, materials,kits, and/or methods, if such features, systems, articles, materials,kits, and/or methods are not mutually inconsistent, is included withinthe inventive scope of the present disclosure.

All definitions, as defined and used herein, should be understood tocontrol over vocabulary definitions, definitions in documentsincorporated by reference, and/or ordinary meanings of the definedterms.

The indefinite articles “a” and “an,” as used herein in thespecification and in the claims, unless clearly indicated to thecontrary, should be understood to mean “at least one.”

The phrase “and/or,” as used herein in the specification and in theclaims, should be understood to mean “either or both” of the elements soconjoined, i.e., elements that are conjunctively present in some casesand disjunctively present in other cases. Multiple elements listed with“and/or” should be construed in the same fashion, i.e., “one or more” ofthe elements so conjoined. Other elements may optionally be presentother than the elements specifically identified by the “and/or” clause,whether related or unrelated to those elements specifically identified.Thus, as a non-limiting example, a reference to “A and/or B”, when usedin conjunction with open-ended language such as “comprising” can refer,in one implementation, to A only (optionally including elements otherthan B); in another implementation, to B only (optionally includingelements other than A); in yet another implementation, to both A and B(optionally including other elements); etc.

As used herein in the specification and in the claims, “or” should beunderstood to have the same meaning as “and/or” as defined above. Forexample, when separating items in a list, “or” or “and/or” shall beinterpreted as being inclusive, i.e., the inclusion of at least one, butalso including more than one, of a number or list of elements, and,optionally, additional unlisted items. Only terms clearly indicated tothe contrary, such as “only one of” or “exactly one of,” or, when usedin the claims, “consisting of,” will refer to the inclusion of exactlyone element of a number or list of elements. In general, the term “or”as used herein shall only be interpreted as indicating exclusivealternatives (i.e. “one or the other but not both”) when preceded byterms of exclusivity, such as “either,” “one of,” “only one of,” or“exactly one of.” “Consisting essentially of,” when used in the claims,shall have its ordinary meaning as used in the field of patent law.

As used herein in the specification and in the claims, the phrase “atleast one,” in reference to a list of one or more elements, should beunderstood to mean at least one element selected from any one or more ofthe elements in the list of elements, but not necessarily including atleast one of each and every element specifically listed within the listof elements and not excluding any combinations of elements in the listof elements. This definition also allows that elements may optionally bepresent other than the elements specifically identified within the listof elements to which the phrase “at least one” refers, whether relatedor unrelated to those elements specifically identified. Thus, as anon-limiting example, “at least one of A and B” (or, equivalently, “atleast one of A or B,” or, equivalently “at least one of A and/or B”) canrefer, in one implementation, to at least one, optionally including morethan one, A, with no B present (and optionally including elements otherthan B); in another implementation, to at least one, optionallyincluding more than one, B, with no A present (and optionally includingelements other than A); in yet another implementation, to at least one,optionally including more than one, A, and at least one, optionallyincluding more than one, B (and optionally including other elements);etc.

It should also be understood that, unless clearly indicated to thecontrary, in any methods claimed herein that include more than one stepor act, the order of the steps or acts of the method is not necessarilylimited to the order in which the steps or acts of the method arerecited.

What is claimed is:
 1. A method implemented by one or more processors,comprising: identifying a particular entity, the particular entity beinga particular person, place, or thing; identifying a plurality of searchqueries that are each associated with the particular entity; determininga query score for each of the search queries, wherein the query scorefor a search query of the search queries is based on entity ambiguity ofthe search query, wherein the entity ambiguity of the search query isbased on a comparison of a quantity of search result documents, for thesearch query, that describe the particular entity to a quantity of thesearch result documents, for the search query, that do not describe theparticular entity; assigning a particular search query of the searchqueries to the particular entity based on the determined query scores;receiving input, the input being provided via a user interface inputdevice of a client computing device; determining that the particularentity is associated with the input; providing, for presentation via auser interface output device of the client computing device, contentthat includes a name of the particular entity and one or more additionalproperties of the particular entity, wherein providing the content is inresponse to the input and is in response to determining that theparticular entity is associated with the input; and in response toselection of the content at the client computing device, submitting theparticular search query to a search engine based on the particularsearch query being assigned to the particular entity.
 2. The method ofclaim 1, wherein the input is a partial search query and the content isa query suggestion for the partial search query.
 3. The method of claim1, wherein the input is a submitted search query.
 4. The method of claim3, wherein the content is an entity summary provided for presentation ina distinct manner from other search results that are responsive to thesubmitted search query.
 5. The method of claim 1, wherein the queryscore for the search query is further based on a similarity measurebetween the query and at least one property of the particular entity. 6.The method of claim 5, wherein the at least one property of theparticular entity includes a trusted name of the particular entity. 7.The method of claim 1, wherein the query score for the search query isfurther based on search result document quality for the search resultdocuments that are associated with the particular entity, and whereinthe search result document quality is based on a document centric signalof the search result documents that are associated with the particularentity.
 8. The method of claim 1, wherein the query score for the searchquery is further based on at least one of: popularity of the searchquery, and search result document quality for the search resultdocuments, for the search query, that are associated with the particularentity.
 9. The method of claim 1, wherein the query score for the searchquery is further based on popularity of the search query, and searchresult document quality for the search result documents, for the searchquery, that are associated with the particular entity.
 10. A system,comprising: one or more non-transitory computer readable media storinginstructions; one or more processors operable to execute theinstructions, wherein the instructions include instructions to: identifya particular entity, the particular entity being a particular person,place, or thing; identify a plurality of search queries that are eachassociated with the particular entity; determine a query score for eachof the search queries, wherein the query score for a search query of thesearch queries is based on search result document quality for searchresult documents, for the search query, that are associated with theparticular entity, wherein the search result document quality is basedon a document centric signal of the search result documents that areassociated with the particular entity; assign a particular search queryof the search queries to the particular entity based on the determinedquery scores; receive input, the input being provided via a userinterface input device of a client computing device; determine that theparticular entity is associated with the input; provide, forpresentation via a user interface output device of the client computingdevice, content that includes a name of the particular entity and one ormore additional properties of the particular entity, wherein providingthe content is in response to the input and is in response todetermining that the particular entity is associated with the input; andsubmit, in response to selection of the content at the client computingdevice, the particular search query to a search engine based on theparticular search query being assigned to the particular entity.
 11. Thesystem of claim 10, wherein the input is a partial search query and thecontent is a query suggestion for the partial search query.
 12. Thesystem of claim 10, wherein the input is a submitted search query. 13.The system of claim 12, wherein the content is an entity summaryprovided for presentation in a distinct manner from other search resultsthat are responsive to the submitted search query.
 14. The system ofclaim 10, wherein the query score for the search query is further basedon a similarity measure between the query and at least one property ofthe particular entity.
 15. The system of claim 14, wherein the at leastone property of the particular entity includes a trusted name of theparticular entity.
 16. The system of claim 10, wherein the query scorefor the search query is further based on entity ambiguity of the searchquery and wherein the entity ambiguity is based on a comparison of aquantity of the search result documents, for the search query, thatdescribe the particular entity to a quantity of the search resultdocuments, for the search query, that do not describe the particularentity.
 17. The system of claim 10, wherein the query score for thesearch query is further based on entity ambiguity of the search queryand popularity of the search query.
 18. At least one non-transitorycomputer readable storage medium storing computer instructionsexecutable by a processor to perform a method comprising: identifying aparticular entity, the particular entity being a particular person,place, or thing; identifying a plurality of search queries that are eachassociated with the particular entity; determining a query score foreach of the search queries, wherein the query score for a search queryof the search queries is based on entity ambiguity of the search query,wherein the entity ambiguity of the search query is based on acomparison of a quantity of search result documents, for the searchquery, that describe the particular entity to a quantity of the searchresult documents, for the search query, that do not describe theparticular entity; assigning a particular search query of the searchqueries to the particular entity based on the determined query scores;receiving input, the input being provided via a user interface inputdevice of a client computing device; determining that the particularentity is associated with the input; providing, for presentation via auser interface output device of the client computing device, contentthat includes a name of the particular entity and one or more additionalproperties of the particular entity, wherein providing the content is inresponse to the input and is in response to determining that theparticular entity is associated with the input; and in response toselection of the content at the client computing device, submitting theparticular search query to a search engine based on the particularsearch query being assigned to the particular entity.